Release Plan Project Name TMH

Note to the Author

This document is a template for a Release Plan that is to be completed for all approved EPMO projets. Release Plan must also be completed for all system/application maintenance releases. The plan is completed during the Planning Phase of the ULC.

The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project:

Blue italicized text enclosed in angle brackets (<text>) provides instructions to the document author or indicates a field that should be replaced with information specific to a particular project.

Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

Purpose

<Briefly describe the purpose and context of the release. This shuld include details such as vendor release, new functionality, new system implementation, etc>

References

<List any other documents or Web addresses to which this Release Plan refers such as the project SharePoint Site, Release Notes, Implementation Plan, Backout Plan, Validation Plan... Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.>

A link is preferred to ensure the reader has access to the latest version of the document(s). Provide a link to Vision document produced as output from Concept phase.

Assumptions/Constraints/Risks

Assumptions

<Describe any assumptions about the current capabilities and use of the solution when it is released in accordance with this plan. Include any information regarding external circumstances or commitments that may impact the release of the solution.

Describe any dependencies that can affect the deployment of the solution. Be sure to identify any other systems or subsystems that this Release Plan directly affects. Describe any dependencies including staffing, divisional/group participation, external system dependencies or dependencies due to specific business cycles that can impact this Release Plan.>

Constraints

<Describe factors that limit the ability to deploy the solution or have some impact on the release of the solution in accordance with this plan (e.g. budget and schedule constraints). Be sure to include constraints due to group’s involvement or any other external system or infrastructure constraints that impact the environment.>

Risks

<Describe any risks associated with release of the solution in accordance with this Release Plan. Identify any adverse impacts to stakeholders (e.g. end users) during the release cycle. Be sure to include any factors that may adversely impact a successful deployment, this should include details of any open defects, as well as the workaround that is in place to address the derfect.>

Release Approach

<Describe the strategy and activities addressed in the planning for the release.>

The Project Name Release Plan provides an outline of activities necessary to ensure that the project’s product is available for use by its end-users as originally planned.

Release Content

<Identify the specific release, including a description of the functionality to be delivered. If the details are extensive, then you can include a link to the release notes in this section. Explain what the proposed system will do (and not do, if necessary). Map individual requirements, if applicable, from the Business Requirements Document to the specific release that will provide that functionality, as appropriate.>

Release Schedule

<Provide a high level schedule for planned delivery of the release and the significant milestones associated with transitioning each release to production.>

Release Impacts

<Describe any business and/or system impacts associated with each release and the business processes that will be modified as a result of the deployment specified in this Release Plan. Identify any systems and interfaces that are directly impacted by the release strategy and any impacts to end users during the release cycle. Describe the relevant benefits, objectives, and goals to be met with each release.>

Release Notification

<If there is release-specific communication that needs to occur that is not already described in the Project Management Plan (Communication Management Plan), please describe here. Specify the individual stakeholders and/or groups requiring notification of an impending release. Also, describe the method for providing notification prior to and/or following successful release of the solution. Specify the information required by each person or group and the timeframes for receipt of the information, prior to release. For example, the helpdesk may require that a notification be received 10 days prior to release.>

Release Management

<Identify the activities used to manage the planning, organization, development, testing, and implementation of new features and functions, defects, change requests, etc. into the application being developed. Identify the individuals involved in a typical release process.

Develop a release checklist to help the project team identify when the product is ready for release for use by the customer.>

Appendix A: References

<Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.>

Table 1 below summarizes the documents referenced in this document.

Document Name	Description	Location
<Document name and version number>	<Document description>	<URL to where document is located>

Table 1 - Appendix A: References

Appendix B: Key Terms

Table 2 below provides definitions and explanations for terms and acronyms relevant to the content presented within this document.

Term	Definition
<Insert Term>	<Provide definition of term and acronyms used in this document>

Table 2 - Appendix B: Key Terms